Release Notes 8.3#1149
Conversation
rasika-chivate
commented
Jul 22, 2026
- Create release notes for version 8.3.
- Update configuration files.
- Include a version selector for 8.3.
|
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 23 out of 23 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (1)
docs/release_notes/8.3.4-1.md:83
- This sentence has two issues: (1) missing space after "and" (renders as "andCompatibility"), and (2) the "Release Notes for MongoDB 8.3" link text points to the 8.3 compatibility URL, which is inconsistent with the label and duplicates the second link.
For the complete list of upstream changes, see [Release Notes for MongoDB 8.3 :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.3-compatibility/){:target="_blank"} and[ Compatibility Changes in MongoDB 8.3 :octicons-link-external-16:](https://www.mongodb.com/docs/manual/release-notes/8.3-compatibility/){:target="_blank"}.
| - Release notes: | ||
| - "Release notes index": "release_notes/index.md" | ||
| - release_notes/8.0.26-11.md | ||
| - release_notes/8.0.23-10.md | ||
| - release_notes/8.0.21-9.md | ||
| - release_notes/8.0.20-8.md | ||
| - release_notes/8.0.19-7.md | ||
| - release_notes/8.0.17-6.md | ||
| - release_notes/8.0.16-5.md | ||
| - release_notes/8.0.12-4.md | ||
| - release_notes/8.0.8-3.md | ||
| - release_notes/8.0.4-2.md | ||
| - release_notes/8.0.4-1.md | ||
| - release_notes/8.3.4-1.md | ||
| - faq.md |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 23 out of 23 changed files in this pull request and generated 2 comments.
Comments suppressed due to low confidence (3)
docs/install/upgrade-from-80.md:3
- The upgrade guide title now says 8.0 → 8.3, but the body still contains multiple 8.0-specific references (e.g., MongoDB 8.0 compatibility link, enabling the
psmdb-80repository, and instructions that appear to install 8.0 packages). This makes the page misleading for 8.3 upgrades; please update the remaining content to consistently target 8.3 (including repo/channel names and external links).
.github/workflows/main.yml:47 - The
stepslist indentation is inconsistent here (the- name: Deploy docsitem is indented one space deeper than other step items). This can make the workflow YAML invalid or change the structure unexpectedly.
- name: Deploy docs
run: |
mike deploy 8.3 -b publish -p
docs/release_notes/8.3.4-1.md:6
- This
---line will render as a horizontal rule at the top of the page. Since the repo uses the Markdownmetaextension (mkdocs-base.yml), you can terminate the metadata block with a blank line instead, avoiding the extra rendered HR.
---
| @@ -0,0 +1,103 @@ | |||
| title: Percona Server for MongoDB release notes version 8.3.4-1 | |||
| summary: Get to know all improvements, new features, and bug and security vulnerability fixes in the release | |||
There was a problem hiding this comment.
the sentence has no ending
|
|
||
| ## Upgrade considerations | ||
|
|
||
| To upgrade to MongoDB 8.3 from an 8.0 deployment, the deployment must have `featureCompatibilityVersion` set to 8.0. |
There was a problem hiding this comment.
Maybe add the link to the upgrade guide?
| To check the version: | ||
|
|
||
| ```javascript | ||
| db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } ) |
There was a problem hiding this comment.
Output will be welcome here, so that users see what to expect
|
|
||
| SBOMs are distributed through the following channels: | ||
|
|
||
| - GitHub: The latest SBOM is placed in the root of the `percona/percona-server-mongodb` main branch. |
There was a problem hiding this comment.
main? Are they the same for every version? Main is not stable as I remember, why would I pull SBOMs for my 8.0 or 7.0 from main?
There was a problem hiding this comment.
in the root of the
percona/percona-server-mongodbmain branch.
This is true but this is not the full truth. Each of the following branches in percona/percona-server-mongodb repository:
master(which was referenced to as "main", I guess),v8.3v8.0,v7.0
actually has its own SBOM. But those per-branch SBOMs are "generic". The final specific SBOMs that get to the deb, rpm, and tar.gz binary packages are generated during packaging by replacing some metainfo in "generic" SBOMs with release-specific values.
Strictly speaking, SBOMs are not "distributed" via GitHub. Their "generic" prototypes are kept there, and a user should not care about that.
Long story short, I suggest removing the whole GitHub bullet point.
|
|
||
| - GitHub: The latest SBOM is placed in the root of the `percona/percona-server-mongodb` main branch. | ||
|
|
||
| - Binaries/Tarballs: An SBOM file is included in `doc/percona-server-mongodb/sbom.cdx.json` |
There was a problem hiding this comment.
And here they are release specific.
There was a problem hiding this comment.
If we remove the GitHub bullet point as suggested above, this one is OK semantically.
I would tune the wording, though. In my humble opinion, the "Binaries" word is somewhat confusing, I'd remove it.
Next, the phrase "An SBOM file is included in doc/percona-server-mongodb/sbom.cdx.json" sounds slightly strange. In the phrase, doc/percona-server-mongodb/sbom.cdx.json is a file, and we get that "An SBOM file is included in file". It makes sense to remove the first "file" word and choose another verb instead of "included".
Combining with a previous point, we can have something like:
- Tarballs: An SBOM is located in the `doc/percona-server-mongodb/sbom.cdx.json` file.
|
|
||
| #### Query planning and aggregation | ||
|
|
||
| The `$scoreFusion` aggregation stage is now generally available, and new expressions support hashing, Extended JSON conversion, binary subtypes, and `ObjectId` generation. |
There was a problem hiding this comment.
Was it tech preview before? In what version? What's the value of it?
There was a problem hiding this comment.
it was Public Preview (term that upstream use). But we haven't released 8.3.x before - so at Percona we did not have that.
|
|
||
| * [PSMDB-2150](https://perconadev.atlassian.net/browse/PSMDB-2150): Percona Server for MongoDB (PSMDB) now provides Software Bills of Materials (SBOMs) for every release. | ||
|
|
||
| * [PSMDB-2003](https://perconadev.atlassian.net/browse/PSMDB-2003): We have implemented caching of LDAP `userToDNMapping` to reduce the number of round-trips to the LDAP server during authentication and authorization. Caching is controlled by `security.ldap.userToDNMapping` (exposed as `--ldapUserToDNMapping` at startup and `ldapUserToDNMapping` at runtime). For detailed information, see our [documentation](https://docs.percona.com/percona-server-for-mongodb/8.3/ldap-parameters.html). |
There was a problem hiding this comment.
Not sure using "we" is appropriate. Rephrase to "Added caching of LDAP...."
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 23 out of 23 changed files in this pull request and generated no new comments.
Comments suppressed due to low confidence (2)
docs/release_notes/8.3.4-1.md:6
- YAML front matter is missing the opening
---delimiter. With only a closing delimiter present, MkDocs won’t parsetitle/authors/version, and{{ page.meta.version }}in the heading will render empty. Add the opening delimiter and normalize theauthorsindentation.
title: Percona Server for MongoDB release notes version 8.3.4-1
summary: Get to know all improvements, new features, and bug and security vulnerability fixes in the release
authors:
- Rasika Chivate
version: 8.3.4-1
---
docs/install/upgrade-from-80.md:6
- The page title/intro now says this is an 8.0 → 8.3 upgrade guide, but the rest of the document still contains 7.0/8.0-specific instructions and references (e.g., MongoDB 8.0 compatibility link, enabling
psmdb-80, setting FCV to8.0, and text saying the upgrade starts with the 7.0 feature set). This makes the guide internally inconsistent and potentially misleading; the remaining steps need to be updated for 8.3.